REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

Good. So this means that the aod-workflow was actually already part of the test?

Yes exactly, it is called by the dpl-workflow.sh script which gets executed in the ASYNC stage of the full-system-test

Error while checking build/O2/fullCI_slc9 for e81801d at 2026-01-23 19:41:

++ cp /sw/slc9_x86-64/O2/14991-slc9_x86-64-local1/compile_commands.json .
+++ python3 -c 'import json, os; print(os.path.commonpath([x["file"] for x in json.loads(open("compile_commands.json").read()) if "sw/BUILD" not in x["file"] and "G__" not in x["file"] and x["file"].endswith(".cxx")]))'
++ O2_SRC=/sw/SOURCES/O2/14991-slc9_x86-64/0
++ [[ -e /sw/SOURCES/O2/14991-slc9_x86-64/0/CMakeLists.txt ]]

Full log here.